Atari Mega Archive 1/Atari Mega Archive - Volume 1.iso/lists/gem/l_1199/1009

Internet Message Format | 1994-08-27 | 2KB

From: "Kevin O'Donovan" <[e-mail]>
Subject: Re: Gem List (Please Post!) (fwd)
Date: Mon, 25 Jul 1994 12:34:48 +0100 (BST)
In-Reply-To: <[e-mail]> from "Michel Forget" at Jul 20, 94 11:48:12 pm
Precedence: bulk

> evil thing.  You also mentioned that only the things you need get
> linked in.  That is to the good, and would make me consider your
> library thoughtfully before making a decision.
>
Needless to say this is the case for any sensibly written library, since it
is a function of the linker to pull in only those modules that are accessed.
This is why its more important than usual to put things in sensible files
when writing a library - if you implemented string.h and put everything in
one source file, then the whole string.h sould get linked in whenever you
used any function in it.

> > WinLIB PRO is easy to use, as the extended functionality is simply
> > intuitive extensions of what the user already knows. Unlike some of
> > atari's 'extended features' which are decidedly non-intuitive. WinLIB
> > strives to have a CONSISTENT, INTUITIVE user interface, whereas
> > 'other' people seem to strive for exactly the opposite :-)
This is all, of course, in your opinion. How many of us here have any
background in this sort of field? I suspect very few. My day job is writing
X user interfaces but I still don't think this qualifies me to make absolute
statements like yours have been. This is why my library is an implementation
of an existing one, ie XView (2.0, though some features from 3.2 are creeping
in). I figure that by implementing a standard and well used library I'm more
likely to be writing something that people will actually find useful.

Kev

--
Kevin O'Donovan
[e-mail]
[e-mail]

I know Karate, Kung Fu, and 47 other dangerous words